Overview of Process+ Action Objects

A Process+ Action Object is a user defined configuration of control loop information, which is deployed online for loop monitoring. When adding a control loop to the Action Object for monitoring, the Action Object is configured to read data from a defined data source, and to read the defined control loop information from a specified .csv file - the loop definitions file.

Process+ Action Objects can be scheduled to deploy on a continuous, constant basis and thus generate Process+ KPIs according to the defined schedule, or they can be deployed on an ad hoc basis, for a once off calculation of Process+ KPIs.

Note: There is a maximum limit of 500 loops that can be deployed per Process+ Action Object. The deployment needs to be split into multiple Action Objects if you have more than 500 loops.

Adding a Process+ Action Object

Open the CSense Runtime Manager and decide whether to add a scheduled AO, or an ad hoc AO. Click [Add] to add a Process+ AO to the CSense Runtime Manager.

Note: This does not add a single control loop to the Process+ AO for monitoring. Rather, it adds a Process+ AO to the CSense Runtime Manager for online deployment.

Deployed Process+ Action Objects

All deployed Process+ Action Objects will be displayed, together with details about that specific Action Object.

Headers

Description

Name

Name of Action Object

Data Collection

Real-time sources: This shows the status of the Action Object's data collection. This data is collected continually, and is used for the Process+ calculations at the end of every shift to generate statistics for each loop.    

The possible states of the data collection for a Process+ Action Object using real-time data:

  • UNINITIALIZED: The data collection has not been initialized yet.

  • INITIALIZED: The data collection has been initialized

  • LOADED: Data collection has been initialized and a blueprint for this request has been loaded successfully into the server.

  • BUILT: All data flows have been built at this stage.

  • RUNTIME INITIALIZED: Data collection has passed its run-time initialization check.

  • RUNTIME PRE-CHECKED: Data collection has passed its run-time pre-check.

  • EXECUTING: Data collection has started successfully.

  • FINISHED: Data collection has finished.

  • SHUTTING DOWN: Data collection is currently shutting down.

  • ERROR: There is a problem with the data collection; data collection has been stopped for this Process+ Action Object. See the Event Viewer for more information on the nature of the error.

    When in an error state: the Process+ Action Object needs to be removed and redeployed. To do this, first export the Action Object configuration, then redeploy the loops in a new Action Object, using the exported data.

 

Read more about data sources, and troubleshooting data availability, for Process+ Action Object data.

 

Historical data sources: This indicates the last time when data was collected for the Action Object to execute. Historical data is always available in historians. At the end of every shift, it is collected from the historian and used for the Action Object that executes, according to the defined execution schedule. The date and time indicated in this column reflect the most recent date and time when data was collected, then used for the most recently calculated Process+ statistics for each loop.

The possible states of the data collection for a Process+ Action Object using historical data:

  • N/A: Data collection has not taken place as yet. The Action Object is scheduled to execute in the future.

  • Date and time: the last time for attempted data collection, which is when the Action Object was scheduled to execute.

Troubleshooting:

Failure in data collection for historical data sources will be indicated by the KPI Schedules column showing an error. Refer to the Event Viewer for more information on the nature of the error. The data collection date and time will still update as data collection is still being attempted.

When in an error state: the Process+ Action Object needs to be removed and redeployed. To do this, first export the Action Object configuration, then redeploy the loops in a new Action Object, using the exported data.

 

Note: Execution of Process+ Action Objects is governed by the setting for error handling as well as the limit to the number of concurrently executable action objects defined for Scheduled Action Objects in the Proficy CSense Run-time Properties dialog box.

Read more about data sources, and troubleshooting data availability, for Process+ Action Object data.

Schedule State

Lists whether the Process+ KPIs are scheduled for generation, have finished generating, or are in an error state.

When an Action Object goes into an error state, this column will show a count of the number of shifts in an error state.

Last Schedule

The time when the last schedule to calculate Process+ KPIs was executed.

Next Schedule

The time when the next schedule to calculate Process+ KPIs will be executed.

When an Action Object goes into an error state, this column will show the next schedule due for the shifts that are not in an error state.

Loops

Number of loops configured in the Action Object

Shifts

A list of all the shifts, by name

Source

Specified data source


Related topics:

  

CSense 2023- Last updated: June 24,2025